home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
answers
/
news
/
inn-faq
/
diff1
< prev
next >
Wrap
Internet Message Format
|
1994-04-05
|
15KB
Path: bloom-beacon.mit.edu!hookup!usc!cs.utexas.edu!uunet!news.mentorg.com!sdl!not-for-mail
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
Newsgroups: news.software.nntp,news.software.b,news.answers
Subject: Changes to INN FAQ Part 1/4: General Information
Supersedes: <inn-faq-changes-1-765518416@Warren.MENTORG.COM>
Followup-To: news.software.nntp
Date: 5 Apr 1994 11:31:03 -0400
Organization: Mentor Graphics - IC Group, Warren, NJ, USA
Lines: 435
Sender: tal@Warren.MENTORG.COM
Approved: news-answers-request@MIT.Edu
Distribution: world
Expires: 04/20/94
Message-ID: <inn-faq-changes-1-764139608@Warren.MENTORG.COM>
Reply-To: Tom_Limoncelli@Warren.MENTORG.COM (Tom Limoncelli)
NNTP-Posting-Host: sdl.warren.mentorg.com
Xref: bloom-beacon.mit.edu news.software.nntp:5493 news.software.b:4175 news.answers:17710
Posted-By: auto-faq 2.4
Archive-name: inn-faq/diff1
[ There was a problem with the 'diff' shell script I was
using. Diffs haven't been properly posted here since
the beginning of the year (maybe longer). So, here are
the diffs since Jan 1. ]
*** 1.50 1994/01/17 14:32:59
--- FAQ-inn.1 1994/03/24 16:59:44
***************
*** 1,4 ****
! Last Changed: $Id: FAQ-inn.1,v 1.50 1994/01/17 14:32:59 tal Exp $
Part 1 of 4
--- 1,4 ----
! Last Changed: $Id: FAQ-inn.1,v 1.65 1994/03/24 16:59:42 tal Exp $
Part 1 of 4
***************
*** 23,28 ****
--- 23,29 ----
Where can I get the latest copy of this FAQ?
What is INN?
What machines does it run on?
+ INN must be really complicated since this FAQ is so long!
Can I run C News with INN?
Can I run NNTP with INN?
Can I run the reference implementation (NNTP1.5) with INN?
***************
*** 31,39 ****
Does INN implement NOV, xthread (trn) or xuser/xmotd (tin) commands?
Is an ident or authorization protocol supported?
Does INN do UUCP batching like C News?
! Help!? How do I configure this beast?
! What can I do if I can't purchase the O'Reiley And
! Associates book on Managing Usenet?
SPECIFIC NOTES FOR SPECIFIC OPERATING SYSTEMS:
AIX tips
--- 32,39 ----
Does INN implement NOV, xthread (trn) or xuser/xmotd (tin) commands?
Is an ident or authorization protocol supported?
Does INN do UUCP batching like C News?
! Help! How do I configure this beast?
! How do I thank the FAQ maintainer?
SPECIFIC NOTES FOR SPECIFIC OPERATING SYSTEMS:
AIX tips
***************
*** 47,52 ****
--- 47,53 ----
Mac running A/UX 3.0
NOV problems on a Pyramid
Warnings to people that must set HAVE_UNIX_DOMAIN to DONT
+ Alpha OSF tips
The FAQ was written by Rich $alz <rsalz@rodan.uu.net> and is now
***************
*** 108,118 ****
--- 109,129 ----
get file faq-inn-4
^D
+ or if you csh and are a total nerd, you can:
+ echo 'get file new-inn.'{1,2,3,4}@ \
+ | tr @ '\012' | mail majordomo@warren.mentorg.com
+ ...or get a real hobby.
+
+
------------------------------
Subject: What is INN?
+ For a complete answer, why not read the Usenix paper that introduced
+ INN to the world? It's available as
+ ftp.uu.net:networking/news/nntp/inn/inn.usenix.ps.Z
+
InterNetNews is a complete Usenet system. The cornerstone of the package
is innd, an NNTP server that multiplexes all I/O. Think of it as an nntpd
merged with the B News inews, or as a C News relaynews that reads multiple
***************
*** 139,144 ****
--- 150,169 ----
------------------------------
+ Subject: INN must be really complicated since this FAQ is so long!
+
+ No, it's just that the FAQ is very complete. Part 2 is so long because
+ it includes a tutorial that tries to turn a beginner into an TCP/IP
+ protocol expert. Part 3 is long because the FAQ maintainer is
+ constantly trying to add every question ever asked on
+ news.software.nntp. Maybe someone should volunteer to maintain an
+ index.
+
+ A lot of the material could be integrated into the Install.ms doc.
+
+
+ ------------------------------
+
Subject: Can I run C News with INN?
No. INN handles all article reception, filing, forwarding, and
***************
*** 260,266 ****
The authd protocol is added to nnrpd by <nhiro@isci.kyutech.ac.jp>.
This unsupported patch can be found in
! ftp.geophys.hokudai.ac.jp:/pub/Network/INN/inn1.4/authd-patch-1.3.tar.gz.
The documentation is in Japanese. Good luck.
In a future release, you will be able to log all POST commands with
--- 285,291 ----
The authd protocol is added to nnrpd by <nhiro@isci.kyutech.ac.jp>.
This unsupported patch can be found in
! ftp.geophys.hokudai.ac.jp:/pub/network/news/inn/patches/authd-patch-1.3.tar.gz
The documentation is in Japanese. Good luck.
In a future release, you will be able to log all POST commands with
***************
*** 286,313 ****
------------------------------
! Subject: Help!? How do I configure this beast?
READ AND FOLLOW THE "Install.ms" FILE. This FAQ is meant to add to
what Install.ms says not replace it.
! You should also purchase the O'Reiley And Associates book on Managing
Usenet to give yourself a good grounding on how to run a site.
------------------------------
! Subject: What can I do if I can't purchase the O'Reiley
! And Associates book on Managing Usenet?
! Hold a fundraiser?
! Seriously, this document will help you some. HOWEVER many people have
! thought that the install.ms doc was incomplete but then re-read the
! "First Time Installation" portion and were amazed how much they missed
! (or just plain skipped) the first time. Personally, I've been a
! newsadmin for too long to be able to know if it would be good for
! beginners. :-)
======================================================================
--- 311,350 ----
------------------------------
! Subject: Help! How do I configure this beast?
READ AND FOLLOW THE "Install.ms" FILE. This FAQ is meant to add to
what Install.ms says not replace it.
! Many people that thought the Install.ms doc was incomplete later
! re-read the "First Time Installation" portion and were amazed how much
! they missed (or just plain skipped) the first time.
!
! You should also purchase the O'Reilly And Associates book on Managing
Usenet to give yourself a good grounding on how to run a site.
------------------------------
! Subject: How do I thank the FAQ maintainer?
! If you find this document useful, please consider making a donation to
! the maintainer's favorite charity:
! The Personal Liberty Fund
! PO Box 11335
! New Brunswick, NJ 08906-1335
! USA
!
! The PLF is a legal and educational organization which helps people in
! New Jersey, USA. They have many on-going projects which range from
! combating youth suicide to legal advocacy. Their Anti-Violence Project
! runs a phone hotline for reporting gay-bashing which helps hundreds of
! people a year. The PLF is an all-volunteer organization and couldn't
! survive without donations. The PLF is recognized by the IRS as a
! 501(c)3 tax-exempt charity. Donations are tax deductible to the
! fullest extent of the law (U.S. citizens only). Please write "INN" in
! the memo field of the check.
======================================================================
***************
*** 329,335 ****
--- 366,394 ----
different compress programm and change config.data accordingly.
(from Kurt Jaeger <pi@rus.uni-stuttgart.de>)
+ Q: innwatch doesn't work well from /etc/inittab, does it?
+
+ Q: Nope. Instead, you can create a "subsystem" with this command:
+
+ mkssys -s innwatch -p /usr/local/news/bin/innwatch -u news -G news -S -n 15 -f 9
+
+ Note that your path to innwatch may differ, depending on where you
+ decided to install the inn components. You also need to enter the
+ command as one long line.
+ This will create a subsystem named "innwatch" belonging to an SRC group
+ named "news". The "-S" means that it uses signals for SRC to tell it
+ when to stop and the "-n" is the SIGTERM signal, for normal shutdown,
+ and the "-f" is the SIGKILL signal, which is sent if the process does
+ not stop within 20 seconds. Then, modify rc.news to issue the command
+
+ startsrc -s innwatch
+
+ to get innwatch going. That's it!
+
+ Shane Castle <swcxt@boco.co.gov, swcxt@csn.org>
+
+
------------------------------
Subject: SunOS 4.1.2 tips
***************
*** 371,376 ****
--- 430,438 ----
Subject: HP-UX tips
+ Q. My logs keep telling me there is no space for articles
+ A. Edit innwatch.ctl to use "bdf" instead of "df".
+
Q. I am running inn on an HP machine. INN won't start up automatically.
I can start it manually. There is no problem with news or INN once
it is started.
***************
*** 386,401 ****
with Posix Session Leader concepts. Ick. (source: Steve Howie
<scotty@piranha.cs.uoguelph.ca>)
! HP-UX 8.07 users might find a problem with getting innwatch to
! start up. People have found that having "at" start it seems
! to work more reliably than other methods:
${DOINNWATCH} && {
! echo "su ${NEWSUSER} -c ${INNWATCH}" | /usr/bin/at now +2 minutes
! # echo "( ( sleep 60 ; ${INNWATCH} ) & )" | su ${NEWSUSER}
}
------------------------------
Subject: Pyramid and system's where only root can have "cron" jobs.
--- 448,466 ----
with Posix Session Leader concepts. Ick. (source: Steve Howie
<scotty@piranha.cs.uoguelph.ca>)
! HP-UX 8.x and 9.x users might find a problem with getting innwatch to
! start up. People have found that having "at" start it seems to work
! more reliably than other methods:
${DOINNWATCH} && {
! echo "${INNWATCH} &" | su ${NEWSUSER} -c 'at now + 2 min' > /dev/null
}
+ The '&' in the command line prevents innwatch from taking up an at-job
+ slot. SysV-style crons have a per-category and overall limit on the
+ number of jobs executing simultaneously.
+
------------------------------
Subject: Pyramid and system's where only root can have "cron" jobs.
***************
*** 434,450 ****
Don't be fooled. Just because it compiles doesn't mean it's going to
work.
!
! ------------------------------
! Subject: Solaris 2.x special needs
- Under Solaris 2.[012] (SunOS 5.0, 5.1, 5.2) you must add the following
- at the beginning of each file using gethostbyname():
! #define gethostbyname __switch_gethostbyname
! Under Solaris 2.3 you still
Under Solaris 2.x (where x = 0, 1, 2 or 3) you need to change
the file "getfqdn.c". Find the lines that read:
--- 499,524 ----
Don't be fooled. Just because it compiles doesn't mean it's going to
work.
! If you start innd on an AT&T SysV Rel 4.0 machine and get syslog
! messages like:
! localhost:15 cant setsockopt(SNDBUF) Protocol error
! localhost:15 cant setsockopt(RCVBUF) Protocol error
! then you should FIRST try to change HAVE_UNIX_DOMAIN to "DONT" in
! config.data. If that doesn't fix the problem, you should comment out
! the "setsockopt()" calls and things will work.
!
! Many SVR4 for i486 binaries (sendmail, mh, vmail, innd, rnews are now
! on ftp.germany.eu.net in pub/comp/i486/svr4/*.SVR4.tgz But remember
! that some of the above need site specific changes, so their usefulness
! may be limited.
! If your SVR4 system still doesn't run correctly, check the
! Solaris 2.x suggestions.
! ------------------------------
! Subject: Solaris 2.x special needs
Under Solaris 2.x (where x = 0, 1, 2 or 3) you need to change
the file "getfqdn.c". Find the lines that read:
***************
*** 458,471 ****
and delete them.
------------------------------
Subject: Mac running A/UX 3.0
! Use the INN malloc.
------------------------------
Subject: NOV problems on a Pyramid
--- 532,586 ----
and delete them.
+ Under Solaris 2.[012] (SunOS 5.0, 5.1, 5.2) you must add the following
+ at the beginning of each file using gethostbyname():
+
+ #define gethostbyname __switch_gethostbyname
+
+ Under Solaris 2.3 gethostbyname() might work without changes depending
+ on your configuration. We haven't figured out when they work and when
+ they don't. If you run into problems, try to change "gethostbyname()"
+ to "solaris_gethostbyname()" and then use the gethostbyname() listed in
+ the Solaris Porting FAQ. This isn't a perfect solution, because you
+ now need a different binary for Solaris 2.[012] systems.
+
+ It would be great if someone were to submit a solaris_gethostbyname()
+ function who's binary works under all Solaris revs and gives all the
+ semantics of BSD gethostbyname(). In particular, one that doesn't have
+ the problems discussed in sun bugid #1126573 or #1135988. It would be
+ amazing if this was submitted by one of the many Sun employees that
+ flame the INN FAQ maintainer in comp.sys.sun.admin everytime he bitches
+ about how much he hates Solaris 2.x. :-)
+
+ Under all Solaris 2.* versions there is a problem with innwatch.ctl.
+ It expects to use "df -i" to find out how many inodes are free on your
+ disk. /usr/{sbin,5bin,bin}/df doesn't support the "-i" option. You
+ have to use "/usr/ucb/df -i" instead, since this version of df includes
+ the "-i" option.
+
------------------------------
Subject: Mac running A/UX 3.0
! Tip #1: Use the INN malloc.
!
! Tip #2: If you are running INN 1.4 on a Mac running A/UX 3.0.1, Every
! so often, (generally when someone fires up a reader), INN goes beserk.
! Syslog says:
!
! innd: ME cant select Bad file number
!
! This message repeats about 20 times per second. It freezes up my
! computer and I need to reboot.
!
! That's a kernel bug. You do have to reboot.
+ If you compiled inn with gcc, don't. My experience was that somehow, if
+ INN was compiled with GCC the kernel bug is triggered, but that doesn't
+ happen with cc.
+
------------------------------
Subject: NOV problems on a Pyramid
***************
*** 521,525 ****
issue the "mode reader" command) or they must read news via the file
system instead of NNTP.
! There is no way around this right now.
--- 636,665 ----
issue the "mode reader" command) or they must read news via the file
system instead of NNTP.
! If you have NNTP-based newsreaders that can't send the "mode reader"
! command, you can try including "server: localhost" in your inn.conf
! file, but then you must have a different inn.conf file for the other
! machines. If you can't do that, you have no other options but to
! recompile your newsreaders.
!
! Remember, if you change your inn.conf file, you must shutdown and
! restart innd. There is no "ctlinnd reload inn.conf" command.
!
!
! ------------------------------
!
! Subject: Alpha OSF tips:
!
! To compile INN for the DEC Alpha, follow the instructions in the INN
! patch archive on ftp.pop.psu.edu:/pub/src/news/inn-patches
!
! In rc.news you need to start $INNWATCH using the following:
!
! ${DOINNWATCH} && {
! echo "${INNWATCH} &" | su ${NEWSUSER} -c 'at now + 2 min' > /dev/null
! }
!
! The '&' in the command line prevents innwatch from taking up an at-job
! slot. SysV-style crons have a per-category and overall limit on the
! number of jobs executing simultaneously.